-
Notifications
You must be signed in to change notification settings - Fork 6
feat: add migrate project from Renku V1 to Renku 2.0 #3527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
You can access the deployment of this PR at https://renku-ci-ui-3527.dev.renku.ch |
07d2242
to
38bf53f
Compare
38bf53f
to
92943a0
Compare
2a3bf74
to
7407a57
Compare
… dev access, refactor migration to use useGetDockerImage in the modal
… to only display error messages when the data is fully loaded.
…n separated components
…r description are not found
- add access to migrate projects to OWNERS and ADMINS - use ExternalLinks component for Learn more buttons and links - remove unnecessary typing - fix copy in Error Alert - use params to get url project URl
7d6452b
to
80cf38b
Compare
leafty
approved these changes
Mar 17, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Tearing down the temporary RenkuLab deplyoment for this PR. |
leafty
pushed a commit
that referenced
this pull request
Apr 22, 2025
- Show migration alert only to project owners and for public projects - Migrate code repository, container image, resource class, description, and keywords - Indicate non-migrated elements during the process - Ensure sessions work if they used a public image in Renku v1 - Block migration if session activation is required in Renku v1 - Allow navigation from Renku v1 projects to their migrated versions in Renku 2.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the ability for project owners to migrate their projects from Renku v1 to Renku 2.0.
Acceptance Criteria
The migration alert is shown only to project owners and for public projects.
The migration process will transfer:
The migration process will display what will not be migrated.
The project is migrated, and a new launcher is added in Renku 2.0.
Sessions should work if they worked in Renku v1 and used a public image.
If a project requires activation in Renku v1 for a session to work, migration is blocked until the project is updated.
Users can navigate from the original project in Renku v1 to the corresponding migrated project in Renku 2.0.
Migrating a project...
Launching a session migrated project:

/deploy renku=release-0.66.0 renku-data-services=andrea/add-projects-migrated renku-notebooks=master